Description

Resolves remaining changes for https://github.com/camunda/product-hub/issues/2126/.

Note a few open questions below, but the overall goal:

- Should the references in the docs be "Camunda user tasks" or "Job worker-based user tasks managed by Camunda"? The latter is rather wordy, but maybe we can figure out a solution. Regardless, this should only be for the 8.7 docs, yes? Should they still be called "Zeebe user tasks" in 8.6 and 8.5?

Additionally, I am planning to make the following changes:

For 8.6

• Document that user tasks with Job worker implementation are deprecated (but supported).
• Explicitly state in migration guide why it is recommended to design a process with one implementation type.

For 8.7

• Note that the Tasklist API will no longer be supported with 8.9 and recommend migrating. Do we need to mark this as deprecated, or rather just note that it is going to be removed but is still supported?
• Remove interactive questionnaire in migration guide
• Rename Zeebe user task to Camunda user task and note terminology change with admonition as the XML may still show Zeebe user task.
• Document that the C8 REST API only supports user tasks with the Camunda user task implementation.
• Document that embedded forms are supported only for Job worker-based user tasks. Is this only for next or also should be backported?
  E.g. this section needs to be updated: https://docs.camunda.io/docs/next/components/modeler/web-modeler/advanced-modeling/form-linking/#camunda-form-embedded

A majority of changes for 8.5 and 8.6 have been launched via PR here, though I plan to launch a separate PR for the changes above.

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support.
• This is already available but undocumented and should be released within a week.
• This on a specific schedule and the assignee will coordinate a release with the DevEx team. (apply hold label or convert to draft PR)
• This is part of a scheduled alpha or minor. (apply alpha or minor label)
• There is no urgency with this change and can be released at any time.

PR Checklist

• My changes are for an already released minor and are in /versioned_docs directory.
• My changes are for the next minor and are in /docs directory (aka /next/).

• My changes require an Engineering review, and I've assigned the Engineering DRI or delegate.
• My changes require a technical writer review, and I've assigned @camunda/tech-writers as a reviewer.